Customizing virtual channels in a discovery interface

ABSTRACT

A unified discovery interface presents broadcast discovery data relating to broadcast content available via a broadcast channel and non-broadcast discovery data relating to non-broadcasting content available via a virtual channel of the unified discovery interface. In one implementation, the virtual channel is customizable via a discovery interface relationship parameter that indicates a relationship of the virtual channel within the unified discovery interface. The unified discovery interface allows a user to select between broadcast media content available via a broadcast channel and non-broadcast media content available via the virtual channel.

BACKGROUND

The convergence of computing and entertainment continues to provide new content and options for consumers. For example, cable subscribers can now access cable television programs and video-on-demand content (VOD) through their set-top boxes. In one offering, video-on-demand service allows a user to select a program for viewing from a library of programs, wherein all of the programs are available at any time and can be paused, saved, reviewed, etc. (as opposed to a cable television program that is only available at a scheduled time and duration). Other sources of content may also exist, including content from a media library, an Internet Protocol (IP) stream, a Web site, etc.

Consumers and content providers can find great benefit in the availability of content from so many different types of sources. For example, a consumer can view a rerun episode of a cable television program and then search for and view a subsequent episode of the same program over VOD or some other content providing channel. For their part, content providers can keep people “tuned in” with a wider assortment of content and content types.

Listings of available programs for a given content source are generated from discovery data (e.g., catalogs of available programming). However, existing approaches for presenting a user with choices of available content from various sources fail to provide a synergistic interface through which to access discovery data for such content. Instead, existing approaches isolate the discovery data for content of each source from the discovery data for content of all other sources. For example, a typical electronic program guide (EPG) provides cable television listings through one interface and video-on-demand content listings through a separate and distinct interface. As such, the discovery interfaces for such content provide no relationships, interactions, or cohesive user experience among content of different sources.

In addition, exhaustively adding extensive volumes of media content available to an existing electronic programming guide would quickly overwhelm the electronic programming guide and make it useless as a tool for a user.

These limitations, therefore, make it more difficult for a consumer to find the content in which they are interested and make it more difficult for a content provider to maintain the consumer's attention.

SUMMARY

Implementations described and claimed herein address the foregoing problems by providing provider or customized selections of broadcast and non-broadcast media content available within an electronic programming guide. In one implementation, for example, discovery data relating to selected non-broadcast content (e.g., streaming video IP content) is collected (e.g., in a catalog) and presented to a user via a virtual channel together with discovery data related to broadcast content in a discovery interface. In this manner, a user can review available broadcast content and selected non-broadcast content via a unified discovery interface and select either type of content for display in customized virtual channels of the unified discovery interface.

The discovery data relating to the non-broadcast content, for example, may include a discovery interface relationship parameter that allows for customizable association and relationships of the virtual channel within the unified discovery interface. For example, where a virtual channel is associated with a broadcast channel, a row of the discovery interface corresponding to the broadcast channel may indicate that broadcast content from a particular television show episode is available at a given timeslot and then, in an adjacent row corresponding to the virtual channel, other episodes of the same show can be listed as available from an non-broadcast content provider, such as a IP content provider. In this manner, the customizable virtual channel can be selectively presented to the user within the context of listed content from another source, thereby intentionally tying together content of potentially common interest to the user within the unified discovery interface.

In some implementations, articles of manufacture are provided as computer program products. One implementation of a computer program product provides a computer program storage medium readable by a computer system and encoding a computer program. Another implementation of a computer program product may be provided in a computer data signal embodied in a carrier wave by a computing system and encoding the computer program. Other implementations are also described and recited herein.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

BRIEF DESCRIPTIONS OF THE DRAWINGS

FIG. 1 illustrates an example system for presenting discovery data pertaining to non-broadcast content in a customized virtual channel of a unified discovery interface.

FIG. 2 illustrates an example screenshot of a unified discovery interface presenting non-broadcast content in a customized virtual channel of a unified discovery interface.

FIG. 3 illustrates another example screenshot of a unified discovery interface presenting non-broadcast content in a customized virtual channel of a unified discovery interface.

FIG. 4 illustrates an example implementation of a system for providing a unified discovery interface.

FIG. 5 illustrates another example implementation of a system for providing a unified discovery interface.

FIG. 6 illustrates example operations for providing non-broadcast content in a customized virtual channel of a unified discovery interface.

FIG. 7 illustrates an example system that may be useful in implementing the described technology.

DETAILED DESCRIPTIONS

FIG. 1 illustrates an example system 100 for presenting discovery data pertaining to non-broadcast content in a customized virtual channel of a unified discovery interface 102. A user's computing system 104 is coupled to a display device 106, which is capable of presenting the unified discovery interface 102. The computing system 104 is also coupled to a tuner device 108 (e.g., a set-top box or a tuner card internal to the computing device), which communicates with a cable content provider 110 and a video-on-demand content provider 112. It should be understood that the cable content provider 110 and the video-on-demand content provider 112 may be represented by the same entity. Furthermore, content providers that compete with the cable providers, such as satellite services and airwave-based broadcast television stations, may also be supported in a similar manner. Content providers for other media, such as satellite radio, broadcast radio, etc., may also be supported through computing system 104.

In one implementation, the computing system 104 executes a media application that manages the user's access to media content, whether available locally or remotely. For example, the user can use his or her computing system 104 to control a portable media player 114, the tuner device 108, a local media library 116, and other content available from discrete devices or over a communications network 118. Examples of the control a user may apply can include without limitations transferring content between a portable media player 114 and a local media library 116, scheduling the recording of a cable television program by a digital video recorder (not shown) coupled to the computing system 104, downloading IP content (such as a video or song) from an IP content provider 120.

In one implementation, the media application also provides the discovery interface 102 on a display device 106 (e.g., a monitor or television) coupled to the computing device 104. Discovery data is obtained through a media information service 122 that collects program information about content from a variety of sources. The media information service 122 maps data from a variety of sources to one or more consistent schema, enabling a consistent discovery experience, and associates content from different sources. The discovery interface 102 can be represented by an on-screen guide, such as an electronic program guide (EPG), although various monikers may be used in other implementations, including without limitation interactive program guide (IPG) and electronic service guide (ESG). The discovery interface 102 presents an on-screen guide to the available content (e.g., broadcast content, such as scheduled cable television programs, and non-broadcast content, such as available IP content, locally stored media, etc.) in which broadcast content and non-broadcast content are shown together via virtual channels of the unified discovery interface.

In one implementation, the discovery interface 102 provides a graphical user interface that can display program titles and other descriptive information (collectively “discovery data”), such as a summary, actors' names and bios, directors' names and bios, year of production, etc. In one implementation, the information is displayed on a grid with the option to select more information on each program, although other formats are also contemplated. Channel identifiers pertaining to the scheduled cable programs, the program start and end times, genres, thumbnail images, and other descriptive metadata can also be presented within the discovery interface 102. Radio and song information may offer other information, such as artist, album, album cover graphics, and track title information. The discovery interface 102 allows the user to browse program summaries; search by genre, channel, etc.; and obtain immediate access to the selected content, reminders, and parental control functions. If the computing device 104 is so configured or so connected, a discovery interface 102 can provide control for scheduled recording of programs.

A user can use the discovery interface 102 to navigate, select, and discover content by a variety of parameters, including time, title, channel, genre, cost, actors, directors, sources, relationships to other content, etc. Navigation can be accomplished through the media application by a variety of input devices, such as a remote control, a keyboard, and a mouse. In one implementation, for example, the user can navigate through the discovery interface 102 and display information about scheduled cable programs, video-on-demand programs, and associated IP content within a single presentation frame. By navigating through the discovery interface 102, the user can manipulate and obtain more information about a current program or about other programs available through the discovery interface 102. For example, when the computing device 104 is connected to a DVR, the user can to plan his or her viewing schedule, learn about the actors of available programs, and record cable programs to a hard disk in the computer device 104 for later viewing.

FIG. 2 illustrates an example screenshot 200 of a unified discovery interface presenting both broadcast content and non-broadcast content via virtual channels of the unified discovery interface. A grid presentation frame presented in the discovery interface includes rows associated with specific broadcast/cable content providers (e.g., networks, local broadcast stations, etc.) and columns associated with designated time slots. The first column 202 identifies the content provider in a selectable promotional region (see e.g., the promotional region 204). By selecting the promotional region 204, a user can navigate to a promotional frame that provides more information about the content provider's offerings.

In the 8:00 PM-9:00 PM time slot for channel “4”, a broadcast content region 206 presents a listing for the program “Alias”, with metadata describing the episode title and an episode summary. By selecting the broadcast region 206, the user can gain access to functionality for changing the viewing channel to broadcast channel “4”, scheduling a reminder to watch “Alias” at 8:00 PM on Thursday, scheduling a recording of the “Alias” episode, and a variety of other actions. The bold line around the broadcast content region 206 indicates that the user has navigated to the broadcast content region 206.

A virtual channel region 208 presents non-broadcast content (e.g., IP content). In this implementation, the virtual channel region 208 is associated with the content provider (i.e., ABC) shown in the promotional region 204 and is presented below the broadcast content region 206 (although other implementations are contemplated). By receiving collected catalog metadata relating to broadcast content and non-broadcast content (e.g., IP content) associated with the broadcast content shown in the broadcast region 206, the unified discovery interface can present discovery information pertaining to the broadcast content and the associated non-broadcast content. As shown in FIG. 3, the user can navigate to the non-broadcast content region 208 to gain access to the non-broadcast content associated with the content provider shown in the promotional region 204.

FIG. 3 illustrates another example screenshot 300 of a unified discovery interface presenting broadcast content together with non-broadcast content. For example, a bold line around a non-broadcast content region 308 indicates that a user has navigated to the non-broadcast IP content region 308 associated with the content provider of channel “4,” (i.e., ABC channel KOMO). Within the non-broadcast content region 308, the user may navigate between multiple non-broadcast content (e.g., IP content) offerings provided by that content provider (or associated content providers). In the implementation of FIG. 3, for example, a user has navigated to a “Lost” episode 310, called “The Other 48 Days”, that is available as IP content within the non-broadcast content region 308. Other options shown in FIG. 3 for the same content provider include “Extreme Makeover,” Boston Legal,” Grey's Anatomy,” “Less than Perfect,” and “Desperate Housewives,” although other IP content may also be available (e.g., from navigating further right or left within the non-broadcast content region 308.

The offerings presented in the non-broadcast content region 308 can be selected by a discovery data ingestion module (see e.g., the discussion regarding FIG. 4) within the context of the associated broadcast channel region 312. For example, if the user navigated from the Alias panel 314 into the non-broadcast content region 308, the offerings listed in the non-broadcast content region 308 can be selected for display based on the user's previous position on the Alias panel 314 (e.g., based on their popularity among people who watch Alias). In alternative implementations, the offerings listed in the non-broadcast content region 308 may be dependent on other information, including appropriateness to the time slot of the user's previous position (e.g., in relation to parental ratings), compliance with parental controls set on the computing system, paid-for/sponsored-positioning within the non-broadcast content region 308, etc.

FIG. 4 shows an example implementation of a system 400 for providing a unified discovery interface. In this implementation, one or more content providers 402 provide discovery data to a discovery data ingestion module 404. The discovery data ingestion module 404 aggregates the discovery data into one or more content compilations, such as a content catalog 406. For example, broadcast content providers, such as cable television providers, provide discovery data specifying broadcast programming details available for electronic programming guides. Likewise, discovery data for available non-broadcast content can be collected into catalogs using web crawlers, search engines, predetermined offerings catalogs, etc. Such discovery data can then be combined into a content catalog 406 for display and activation within the unified discovery interface.

Discovery data related to non-broadcast content received at the discovery data ingestion module 404 can be associated with one or more virtual channel to be presented in the discovery interface. Thus, if a content provider offers non-broadcast content for a particular virtual channel, the content provider may provide discovery data to the discovery data ingestion module 404 that is linked or otherwise associated with that virtual channel. In one particular implementation, for example, the content provider may link or otherwise associate discovery data for non-broadcast content to a particular virtual channel. In this implementation, for example, the content provider may offer a virtual channel directly to its subscribers and provide discovery data for content offered on that virtual channel to the discovery data ingestion module 404 that is linked or otherwise associated with that virtual channel for presentation in the discovery interface.

The virtual channel offered by the content provider may also be associated with another channel (e.g., a broadcast channel or another virtual channel) available through the discovery interface. In this implementation, the discovery data for content to be offered via that virtual channel may include a discovery interface relationship parameter that identifies a relationship of non-broadcast content offered via that virtual channel to the other channel presented via the discovery interface. In the implementation shown in FIG. 3, for example, the non-broadcast content (e.g., the Lost episode 310 entitled “The Other 48 Days”) shown in non-broadcast content region 308 is associated with the ABC content provided via ABC channel “4” KOMO. Thus, the discovery interface relationship parameter associated with this non-broadcast content may identify that the discovery data for this content is to be displayed in association with the broadcast content shown in broadcast content region 312 (e.g., below broadcast content region 312 as shown in FIG. 3).

Alternatively, the discovery data of the non-broadcast content to be presented via a virtual channel in the discovery interface may identify a particular virtual channel it is associated with, and the virtual channel itself may include discovery data or some other parameter identifying the relationship of the virtual channel to some other channel (broadcast or non-broadcast) presented in the discovery interface. In the implementation shown in FIG. 3, for example, a virtual channel (e.g., non-broadcast region 308) is linked with or otherwise associated with the ABC broadcast channel provided in broadcast content region 312 for ABC channel “4” KOMO. In this implementation, discovery data or another parameter of the virtual channel itself may identify that the virtual channel is to be displayed in association with the broadcast channel provided in broadcast content region 312 (e.g., below broadcast content region 312 as shown in FIG. 3).

Where the virtual channel or the non-broadcast content is not associated with a broadcast channel to be presented in the discovery interface, the content provider may provide discovery data for the virtual channel or the non-broadcast content may include a discovery interface relationship parameter that identifies a location (absolute or relative) within the discovery interface for which the discovery data is to be displayed. The discovery interface parameter may identify, for example, a channel number or another location within the discovery interface at which the virtual channel or the non-broadcast content may be presented to a user.

In yet another implementation, the discovery data ingestion module 404 may associate discovery content of non-broadcast content provided by the content providers with one or more virtual channel, either directly or via a discovery data customization interface 426. In this implementation, the discovery data ingestion module 404 receives discovery data for non-broadcast content from the content providers and links or otherwise associates this content with one or more virtual channel.

The discovery data ingestion module 404 can also receive and/or provide billing data 408 and advertising data, such as in an advertising catalog 410. Billing data 408, for example, may be used to process financial transactions through the discovery interface, such as a viewer purchasing media or ordering VOD content. Advertising data may be used to present advertisements through the discovery interface and potentially to tailor advertisements for individual viewers or families, in a similar manner as cookies for web sites. A media client 412 receives the discovery data from the one or more content compilations, billing data 408, and/or advertising data.

The metadata ingestion module 404, for example, can receive discovery data, such as metadata related to content provided (or to be provided) by a content provider. Metadata may include, without limitation, descriptive properties of content or descriptive properties of how the content is integrated within the unified discovery interface. Metadata describing media content, for example, may include title, synopsis, genre, category, classification, review, cast, crew, artist, producer, time, duration, location, content type, content provider, source, resolution, cost, subscriber, or other data relating to particular media content. Metadata describing integration within the discovery interface (e.g., a discovery interface relationship parameter) may include without limitation descriptions of the contextual, demographic, or parental ratings relationships of the content with other content. For example, contextual relationships may associate content directed to a common subject matter (e.g., World War II) or genre (e.g., “The 4400”, “The X-files”). Demographic relationships may associate content directed to viewers in certain age groups (e.g., a viewer browsing through Nickelodeon and/or Cartoon Network broadcast programming may see IP content directed to viewers in the 5-14 year old age group). Parental ratings relationships may prevent the display of IP content based on parental controls set up on the computing system.

The discovery data ingestion module 404 receives discovery data from one or more content providers 402 and aggregates the discovery data into one or more compilations of discovery data (such as a catalog, an index, a database, etc.). In one particular implementation, for example, the discovery data ingestion module 404 aggregates discovery data relating to broadcast content and non-broadcast content into a single compilation, such as a content catalog 406. Alternatively, the discovery data ingestion module 404 may aggregate discovery data relating to broadcast content and non-broadcast content into separate compilations, such as independent content catalogs or independent files or repositories stored within a single compilation (e.g., a catalog, index, database, etc.). The content catalog 406, for example, may include one or more repositories for metadata, such as depending on the type of content delivery by which particular content is available. In one implementation, the content catalog 406 may include a repository for broadcast content (e.g., time-based programming media content) metadata (e.g., an electronic programming guide), such as broadcast television, broadcast radio, cable television, cable audio, satellite television, satellite audio, or other broadcast content.

The content catalog 406 may further include a repository for non-broadcast content, such as Internet protocol content provided by a broadcast content provider or its sponsored or associated content providers. This “approved” Internet protocol content repository, for example, may include metadata for approved Internet protocol media content or Internet protocol media content provided by an approved or sponsor partner content provider. This repository, for example, may be downloaded or otherwise provided directly to a media client 412 (e.g., a user media content delivery device) to allow for quicker searching and response within unified discovery interface.

The media catalog may also include a “non-approved” Internet protocol repository. Such a non-approved repository, for example, may include metadata for media content accessible via a network (e.g., the Internet or another wide area network (WAN)). In this manner, the provider of a unified discovery interface may allow for access to a wide variety of content without being responsible for the quality or subject matter of the media content.

“Long tail” media content available, for example, on the Internet includes low circulation media content that, while not necessarily popular with the general public, may be especially relevant to interests of individual customers. In one particular implementation, for example, an end-user may provide a profile or other identifier of types of media content that are of interest and/or the unified discovery interface may predict media content that may be of interest based upon previous viewing of or listening to media content. In such an implementation, the unified discovery interface may provide a repository of suggested media content that may have been identified by sorting, searching, crawling, or otherwise analyzing of a larger repository based upon a particular user profile or prediction of user interest. In another implementation, a user may register with a third party provider to allow metadata for the third party's media content to appear in such a repository for use in a virtual channel of that user's personal unified discovery interface.

Such long tail media content may be available in enormous quantities and at various quality levels such that differentiation from media content provided by the provider or approved content providers of the unified discovery interface may be useful. However, metadata for such approved and non-approved Internet protocol media content may be combined into a single repository, or completely other repository arrangements may even be used. In addition, any repositories of discovery data may be downloaded or otherwise provided to the media client 412 or may be remotely accessible by the media client 412.

Other types of data, such as billing data 408 and an advertising catalog 410, may also be provided to or otherwise accessible by the media client 412 to authorize a purchase of media content where required or to provide advertisements for display within a unified discovery interface or during presentation of media content on a presentation device 414.

The media client 412 receives discovery data from the content catalog 406. As described above, the discovery data for non-broadcast content may already be linked or otherwise associated with one or more virtual channel, such as by the content providers 402 and/or at the discovery data ingestion module 404. In another implementation, the discovery data for non-broadcast content may be linked or otherwise associated with one or more virtual channel at the media client 412.

In one implementation, for example, a compilation of discovery data is received from the content catalog 406 at the media client 412 and one or more virtual channel is customized at the media client 412. A media client customization interface 428 is provided to allow customization of a virtual channel at the media client 412. The media client customization interface 428, for example, may be used by a third party, such as a user or a content provider, to update or provide new discovery data for non-broadcast content that may be presented in a virtual channel of a unified discovery interface. The user may, for example, program the media client 412, such as through local settings stored on the media client 412, via the media client customization interface 428 to select and associate certain media content with one or more virtual channels. In this manner, the user can identify non-broadcast content to be presented via a virtual channel in the unified discovery interface.

A third party, such as a content provider or OEM, may directly select or associate non-broadcast content with one or more virtual channels via the media client customization interface 428 (e.g., by updating or providing new discovery data, such as a discovery interface relationship parameter) to define one or more virtual channels to be presented via the unified discovery interface. The user or content provider may use the media client customization interface 428 at different times (e.g., periodically) in order to provide changing non-broadcast content available through the unified discovery interface.

In one implementation, for example, the media client 412 uses a subscription protocol, such as Really Simple Syndication (RSS), to periodically pull discovery data from a source external to the content catalog 406. In this implementation, a user or third party content provider can subscribe to content feeds outside of the media client discovery interface (e.g., through a web site) and have that feed appear in the discovery interface and be automatically updated. For example, a user may subscribe by navigating to a new Internet content provider (e.g., Rocketboom) or related web site that hosts family video content. The user can subscribe to the video content at the web site. The media client 412 then periodically polls the content source to determine if new content was available. When new content is available, the media client 412 provides that content to a user via a virtual channel in the discovery interface (e.g., the family channel). The user could define how content subscriptions are aggregated into particular virtual channels of the discovery interface. For example, the user can direct content from multiple sources into a single virtual channel or may opt to create separate virtual channels for each source.

A discovery interface manager 414 of the media client 412 uses this discovery data to generate and present a unified discovery interface to a user (e.g., via a presentation device 420). The unified discovery interface provides the user with a choice between broadcast content available via a broadcast channel and non-broadcast content available via a virtual channel. When a user selects particular media content from the unified discovery interface, a content manager 418 receives the content media and presents the content media to a media player 419 and then ultimately to the user on a presentation device 420. The content manager 418 may, for example, receive the media content from a personal media library 416 and/or content sources 422 and 424 associated with one or more of the content providers 402.

The content catalog 406 may, for example, contain metadata that defines an actual media content source, such as a unique identifier for that content, a source type (e.g., television or IP), and a method or protocol for accessing or retrieving the metadata (e.g., a tuning request for a live television program or an HTTP GET request and a URL to the content on an Internet server for IP content). When the user selects a particular media content via the discovery interface, the discovery interface manager accesses the metadata associated with the media content from the content catalog 406, such as using an ID reference and launches the appropriate content retrieval function based on its source type and access method. The content catalog 406 may also include metadata that allows the media client 412 to determine which promotional link is displayed (e.g., on a broadcast or other channel). For example, if a user selects the show Alias from channel 4, the content manager 418 directs an NTSC tuner to receive the Alias broadcast. Likewise, if the user selects the Lost episode from ABC.com, the content manager 418 establishes an appropriate video stream from the specified URL. If the user selects to purchase the episode of Lost from CinemaNow or Movielink, the content manager 418 initiates a download from the specified URL.

In one particular implementation, for example, the content compilation 406 includes a source field for each content entry. The source field may indicate a content delivery type (e.g., broadcast delivery or IP content delivery), which can be used to direct the content manager 418 to an appropriate source for the selected content. In addition, a promotional link to a promotional portal of the content provider can also be matched to the source field of the content compilation 406. For example, an ABC source field may be used to map ABC promotional links to ABC content. The discovery interface manager 414 of the media client 412 may also be used to determine which, if any, of the channels should receive a promotional link to a promotional portal. For example, the promotional link may only be used for the first affiliated channel in the discovery interface or only for the local affiliate, if multiple affiliates are included in the interface. In addition, the discovery interface manager 414 may also be used to block certain promotional links from appearing within the discovery interface, such as where promotion of content is blocked by a content provider.

The download manager, for example, may receive broadcast content via broadcast delivery methods, such as time-based programming content delivery, analog terrestrial broadcast content delivery, digital terrestrial broadcast content delivery, pay television broadcast content delivery, and the like. The download manager 418 may also receive non-broadcast content via non-broadcast delivery methods, such as Internet protocol content delivery, video-on-demand content delivery, digital video recorder content delivery, digital video disc content delivery, compact disc music content delivery, video cassette recorder content delivery, platform partner content delivery, web content delivery, longtail content delivery, and other types of remote non-broadcast media content delivery. Local media content, such as available via the personal media library 416, may also be included in a unified discovery interface.

As described above, a user can select particular broadcast content or non-broadcast content for presentation from the unified discovery interface. The download manager 418 residing on the media client 412 receives the selected media content and presents it on the presentation device 420 via a content player interface (not shown). The selected media content, for example, may be received from a remote content source 422 or 424. The remote content sources 422 and 424 may, for example, be associated with one or more content providers 402 or may be accessible from other content providers, such as longtail content providers accessible via the Internet or another WAN. Television or radio broadcast programming content, for example, may be received and selected via a tuner in the media client 412 from a broadcast media content source, a cable source, a satellite source, or other type of television or radio broadcast content delivery. Non-broadcast content, such as Internet protocol media content, may also be received from a server via a network, such as the Internet. Other types of media content delivery are also contemplated.

FIG. 5 shows an example implementation of a system 500 for providing a unified discovery interface. In this implementation, the system 500 includes a media client 512. The media client 512 includes local data storage, such as a hard drive, for storing a database 516 of discovery content for use in a unified discovery interface 518. The database 516 includes a broadcast discovery data repository 520 and a non-broadcast discovery data repository 522. The data repositories 520 and 522 can include, for example, separate file structures or tables within the database 516. The broadcast discovery data repository 520 includes discovery data related to broadcast content available via broadcast channels of the unified discovery interface 518 (e.g., broadcast television content). The non-broadcast discovery data repository 522 includes discovery data related to non-broadcast content available via virtual channels of the unified discovery interface 518 (e.g., IP content). In one particular implementation, for example, the repositories of the database 516 store discovery data in a material exchange format (MXF) file format. MXF is a “container” or “wrapper” format that supports a number of different streams of coded “essence,” encoded with any variety of codecs, together with a metadata wrapper that describes the material contained within the MXF file. Other file formats for storing discovery data can also be used.

Table 1, shown below, shows one example of an MXF data structure. Other data structures may also be used.

TABLE 1 Example data structure for an MXF file. <MXF version=“1.0”>  <Assembly name=“mcstore.dll” Version=“6.0.5045.0”>   <nameSpace=“Microsoft.MediaCenter.Store”>    <Type name=“StoredObject”/>    <Type name=“Provider”/>    <Type name=“FieldRestriction”/>    <Type name=“UId” parentFieldName=”target”/>   </namespace>  </Assembly>  <Assembly name=“mcepg.dll” Version=“6.0.5045.0”>   <nameSpace=“Microsoft.MediaCenter.Guide”>    <Type name=“Serv”/>    <Type name=“TuneReq”/>    <Type name=“ATSCTuneRequest”/>    <Type name=“Channel”/>    <Type name=“ChannelLineup”/>    <Type name=“Program”/>    <Type name=“ScheduleEntry” groupName=“ScheduleEntries”/>   </namespace>  </Assembly>  <Provider id=“WMIS”>   <UId nameSpace=“Microsoft.MediaCenter.ProviderNames” idValue=“WMIS”/>  </Provider>  <StoredObjects provider=“WMIS”>  <TuneRequests>    <ATSCTuneRequest id=”tr4.1” phys=”38” major=”4” minor=”1”/>    <ATSCTuneRequest id=”tr5.1” phys=”48” major=”5” minor=”1”/>    <ATSCTuneRequest id=”tr7.1” phys=”39” major=”7” minor=”1”/>   </TuneRequests>   <Services>    <Serv id=”KOMO-DT” name=”KOMO-DT” callSign=“KOMO-DT“ affil=”CBS” tuneReq=”tr4.1”/>    <Serv id=”KING-DT” name=”KING-DT” callSign=“KING-DT“ affil=”NBC” tuneReq=”tr5.1”/>    <Serv id=”KIRO-DT” name=”KIRO-DT” callSign=“KIRO-DT“ affil=”ABC” tuneReq=”tr7.1”/>   </Services>   <ChannelLineup name=”ATSC - 98052”>    <Channels>     <Channel name=”1041” service=”KOMO-DT”/>     <Channel name=”1051” service=”KING-DT”/>     <Channel name=”1071” service=”KIRO-DT”/>    </Channels>   </ChannelLineup>   <Services>    <Serv id=”KOMO-DT” name=”KOMO-DT” callSign=“KOMO-DT“ affil=”CBS” tuneReq=”tr4.1”/>    <Serv id=”KING-DT” name=”KING-DT” callSign=“KING-DT“ affil=”NBC” tuneReq=”tr5.1”/>    <Serv id=”KIRO-DT” name=”KIRO-DT” callSign=“KIRO-DT“ affil=”ABC” tuneReq=”tr7.1”/>   </Services>   <Programs>    <Program id=”p1” title=”Lost” episodeTitle=”Weird Stuff Happens”>     <UId namespace=”WMIS.ProgramIds” idValue=”1234”>     <Description>     example description.     </Description>    </Program>   </Programs>   <ScheduleEntries service=”KOMO-DT”>    <ScheduleEntry program=”p10”/>    <ScheduleEntry program=”p11”/>   </ScheduleEntries>   <ScheduleEntries service=”KING-DT” >    <ScheduleEntry program=”p20” startTime=”xxx” endTime=”xxx”/>    <ScheduleEntry program=”p21” startTime=”xxx” endTime=”xxx”/>   </ScheduleEntries>   <ScheduleEntries service=”KING-DT”>    <ScheduleEntry program=”p20” startTime=”xxx” endTime=”xxx”/>    <ScheduleEntry program=”p21” startTime=”xxx” endTime=”xxx”/>   </ScheduleEntries>   <ScheduleEntries service=”KIRO-DT”>    <ScheduleEntry program=”p30” startTime=”xxx” endTime=”xxx”/>    <ScheduleEntry program=”p31” startTime=”xxx” endTime=”xxx”/>   </ScheduleEntries>  </StoredObjects> </MXF>

When the unified discovery interface 518 is accessed, discovery data from the broadcast discovery data repository 520 and the non-broadcast discovery data repository 522 is provided to a class module 524 that provides an abstraction layer, receives the discovery data from the repositories of the database 516 and combines them into broadcast channels and virtual channels for presentation in the unified discovery interface 518.

The class module 524 receives non-broadcast discovery data associated with a virtual channel from the non-broadcast discovery data repository 524 of the database 516 and determines how to combine it with the broadcast discovery data of a broadcast channel in the unified discovery interface 518. Where the virtual channel is associated with a broadcast channel, for example, the class module 524 receives a discovery interface relationship parameter associated with the virtual channel. As described above, the discovery interface relationship parameter indicates a broadcast channel of the discovery interface associated with that virtual channel. The class module 524 uses this discovery interface relationship parameter to identify the associated broadcast channel and determine a location for presenting the virtual channel within the unified discovery interface 516 in some relation to a location of the associated broadcast channel (e.g., above, below, alongside, or some other relation). Although the above implementation describes a virtual channel being associated with a broadcast channel, the virtual channel may also be associated with another virtual channel. Other implementations are also contemplated.

The discovery interface relationship parameter may specify, for example, a network or channel associated with the virtual channel, a title of an affiliate of a broadcast channel, programming metadata (e.g., layout and timing parameters), relationship parameters tying the virtual channel to a given entry of the unified discovery interface, or the like.

Where the virtual channel is not associated with a broadcast channel or another virtual channel, the class module 524 receives the discovery interface relationship parameter associated with the virtual channel. The class module 524 uses this discovery interface relationship parameter to determine a location (absolute or relative) for presenting the virtual channel within the unified discovery interface 516. Other implementations are also contemplated.

The discovery data stored in one or more of the repositories of the database 516 can be refreshed or otherwise updated at different times (e.g., periodically, at idle system times, or at other times). In one particular implementation, for example, the discovery data is refreshed via an MXF loader 526 that updates data in one or both of the broadcast discovery data repository 520 and the non-broadcast discovery data repository 522.

FIG. 6 illustrates example operations 500 for customizing a virtual channel in a unified discovery interface. First discovery data related to broadcast media content available via a broadcast channel of a unified discovery interface is received in a receipt operation 502. The discovery data may be received, for example, from a content provider for the broadcast media content, a content delivery provider (e.g., a broadcaster, cable provider, or satellite provider), a personal media library, or other sources of discovery data. The discovery data may include metadata, such as content-related metadata and metadata that describes integration of media content within the unified discovery interface. Metadata, for example, may include title, synopsis, genre, category, classification, review, cast, crew, artist, producer, time, duration, location, content type, content provider, source, resolution, cost, subscriber, or other data relating to particular media content.

Second discovery data related to non-broadcast media content available via a virtual channel of the unified discovery interface is received in another receipt operation 504. The first and second discovery data received in the receipt operations 502 and 504 may be received (directly or indirectly) from the same or from different content providers. The broadcast media content, for example, may include time-based programming, such as broadcast television, cable television, or satellite television, while the non-broadcast media content, for example, may include an alternative non-broadcast media content, such as video-on-demand, IP programming available via the Internet or another WAN, locally-stored media content, such as from a personal media library, and the like.

The virtual channel comprises a discovery interface relationship parameter indicating a relationship of the virtual channel within the unified discovery interface. The discovery interface relationship parameter, for example, may indicate a relationship of the virtual channel to another channel available via the unified discovery interface, such as a broadcast channel or another virtual channel. The discovery interface relationship parameter may alternatively indicate a location relationship of the virtual channel within the unified discovery interface, such as at a particular channel number or in relation to one or more other channels.

The first and second discovery data is presented via a unified discovery interface through which a user may select between the broadcast media content available via the broadcast channel and the non-broadcast content available via the virtual channel in a presentation operation 506. In one implementation, a client module presents the unified discovery interface to the user via a presentation device. The user can then review discovery data in the unified discovery device for media content available via both broadcast channels and virtual channels and select one or more media content for presentation from that interface.

A selection of broadcast media content available via the broadcast channel or the non-broadcast media content available via the virtual channel is received via the unified discovery interface in a selection operation 508. The selected media content is then received from a content source in a receipt operation 510 and is presented to a user via a presentation device in a presentation operation 512.

The example hardware and operating environment of FIG. 7 for implementing the invention includes a computing device, such as general purpose computing device in the form of a gaming console or computer 20, a mobile telephone, a personal data assistant (PDA), a set top box, or other type of computing device. In the implementation of FIG. 7, for example, the computer 20 includes a processing unit 21, a system memory 22, and a system bus 23 that operatively couples various system components including the system memory to the processing unit 21. There may be only one or there may be more than one processing unit 21, such that the processor of computer 20 comprises a single central-processing unit (CPU), or a plurality of processing units, commonly referred to as a parallel processing environment. The computer 20 may be a conventional computer, a distributed computer, or any other type of computer; the invention is not so limited.

The system bus 23 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, a switched fabric, point-to-point connections, and a local bus using any of a variety of bus architectures. The system memory may also be referred to as simply the memory, and includes read only memory (ROM) 24 and random access memory (RAM) 25. A basic input/output system (BIOS) 26, containing the basic routines that help to transfer information between elements within the computer 20, such as during start-up, is stored in ROM 24. The computer 20 further includes a hard disk drive 27 for reading from and writing to a hard disk, not shown, a magnetic disk drive 28 for reading from or writing to a removable magnetic disk 29, and an optical disk drive 30 for reading from or writing to a removable optical disk 31 such as a CD ROM or other optical media.

The hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to the system bus 23 by a hard disk drive interface 32, a magnetic disk drive interface 33, and an optical disk drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computer 20. It should be appreciated by those skilled in the art that any type of computer-readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROMs), and the like, may be used in the example operating environment.

A number of program modules may be stored on the hard disk, magnetic disk 29, optical disk 31, ROM 24, or RAM 25, including an operating system 35, one or more application programs 36, other program modules 37, and program data 38. A user may enter commands and information into the personal computer 20 through input devices such as a keyboard 40 and pointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial port interface 46 that is coupled to the system bus, but may be connected by other interfaces, such as a parallel port, game port, or a universal serial bus (USB). A monitor 47 or other type of display device is also connected to the system bus 23 via an interface, such as a video adapter 48. In addition to the monitor, computers typically include other peripheral output devices (not shown), such as speakers and printers.

The computer 20 may operate in a networked environment using logical connections to one or more remote computers, such as remote computer 49. These logical connections are achieved by a communication device coupled to or a part of the computer 20; the invention is not limited to a particular type of communications device. The remote computer 49 may be another computer, a server, a router, a network PC, a client, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 20, although only a memory storage device 50 has been illustrated in FIG. 6. The logical connections depicted in FIG. 6 include a local-area network (LAN) 51 and a wide-area network (WAN) 52. Such networking environments are commonplace in office networks, enterprise-wide computer networks, intranets and the Internet, which are all types of networks.

When used in a LAN-networking environment, the computer 20 is connected to the local network 51 through a network interface or adapter 53, which is one type of communications device. When used in a WAN-networking environment, the computer 20 typically includes a modem 54, a network adapter, a type of communications device, or any other type of communications device for establishing communications over the wide area network 52. The modem 54, which may be internal or external, is connected to the system bus 23 via the serial port interface 46. In a networked environment, program modules depicted relative to the personal computer 20, or portions thereof, may be stored in the remote memory storage device. It is appreciated that the network connections shown are example and other means of and communications devices for establishing a communications link between the computers may be used.

In an example implementation, a discovery data ingestion module, a download module, a discovery interface module, a class module, and other modules may be embodied by instructions stored in memory 22 and/or storage devices 29 or 31 and processed by the processing unit 21. A personal media library, various catalogs, databases, and content, and other data may be stored in memory 22 and/or storage devices 29 or 31 as persistent datastores.

The technology described herein is implemented as logical operations and/or modules in one or more systems. The logical operations may be implemented as a sequence of processor-implemented steps executing in one or more computer systems and as interconnected machine or circuit modules within one or more computer systems. Likewise, the descriptions of various component modules may be provided in terms of operations executed or effected by the modules. The resulting implementation is a matter of choice, dependent on the performance requirements of the underlying system implementing the described technology. Accordingly, the logical operations making up the embodiments of the technology described herein are referred to variously as operations, steps, objects, or modules. Furthermore, it should be understood that logical operations may be performed in any order, unless explicitly claimed otherwise or a specific order is inherently necessitated by the claim language.

The above specification, examples and data provide a complete description of the structure and use of example embodiments of the invention. Although various embodiments of the invention have been described above with a certain degree of particularity, or with reference to one or more individual embodiments, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from the spirit or scope of this invention. In particular, it should be understood that the described technology may be employed independent of a personal computer. Other embodiments are therefore contemplated. It is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative only of particular embodiments and not limiting. Changes in detail or structure may be made without departing from the basic elements of the invention as defined in the following claims.

Although the subject matter has been described in language specific to structural features and/or methodological arts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts descried above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claimed subject matter. 

1. A method of presenting a customized virtual channel including non-broadcast content within a unified discovery interface, the method comprising: receiving first discovery data related to broadcast media content available via a broadcast channel; receiving second discovery data related to non-broadcast media content to be presented for selection via a virtual channel in a unified discovery interface, the virtual channel comprising a discovery interface relationship parameter indicating a relationship of the virtual channel within the unified discovery interface; and presenting the unified discovery interface comprising the broadcast channel and the virtual channel through which a user may select between the broadcast media content and the non-broadcast media content, wherein a location of the virtual channel is determined based upon the discovery interface relationship parameter.
 2. The method of claim 1 wherein the first discovery data comprises metadata relating to the broadcast media content available via the broadcast channel.
 3. The method of claim 1 wherein the first discovery data further comprises metadata relating to a relationship between the broadcast media content and other media content.
 4. The method of claim 1 wherein the receiving the first discovery data operation comprises downloading a compilation of data including the first discovery data from a server via a wide area network.
 5. The method of claim 4 wherein the compilation further comprises the second discovery data relating to the non-broadcast media content available via the virtual channel presented in the unified discovery interface.
 6. The method of claim 4 wherein the receiving the second discovery data comprises downloading a second compilation of data including the second discovery data from a server via a wide area network.
 7. The method of claim 1 wherein non-broadcast content associated with the virtual channel is selectable by a user via local settings of a media client.
 8. The method of claim 1 wherein the non-broadcast content associated with the virtual channel is received via a subscription.
 9. The method of claim 1 wherein the non-broadcast content associated with the virtual channel is selectable by a third party via a media client interface.
 10. The method of claim 1 wherein the non-broadcast media content comprises Internet Protocol media content.
 11. A media content delivery device for presenting a customized virtual channel including non-broadcast media content within a unified discovery interface, the media content delivery device comprising: a discovery interface that presents first discovery data relating to broadcast media content available via a broadcast channel and second discovery data relating to non-broadcast media content available via a virtual channel in a unified discovery interface and receives a user selection of a particular media content for presentation; and a content player interface that provides the particular media content for presentation.
 12. The media content delivery device of claim 11 further comprising a tuner for selecting between a plurality of individual broadcast media content.
 13. The media content delivery device of claim 11 further comprising a media client interface that updates the second discovery data.
 14. The media content delivery device of claim 11 wherein the non-broadcast media content comprises Internet Protocol media content.
 15. The media content delivery device of claim 11 wherein the second discovery data comprises metadata relating to the non-broadcast media content available via the virtual channel of the unified discovery interface.
 16. The user content delivery device of claim 11 wherein the second discovery data comprises a discovery interface relationship parameter relating to a relationship between the virtual channel and another channel of the unified discovery interface.
 17. A computer-readable medium having computer-executable instructions for performing a computer process that implements the operations comprising: receiving first discovery data related to broadcast media content available via a broadcast channel; receiving second discovery data related to non-broadcast media content to be presented for selection via a virtual channel in a unified discovery interface, the virtual channel comprising a discovery interface relationship parameter indicating a relationship of the virtual channel within the unified discovery interface; presenting the unified discovery interface comprising the broadcast channel and the virtual channel through which a user may select between the broadcast media content and the non-broadcast media content, wherein a location of the virtual channel is determined based upon the discovery interface relationship parameter receiving a user selection of a particular media content for presentation; and providing the particular media content for presentation.
 18. The computer-readable medium of claim 17 wherein the second discovery data comprises metadata relating to the non-broadcast media content available via the virtual channel of the unified discovery interface.
 19. The computer-readable medium of claim 17 wherein the second discovery data further comprises a discovery interface relationship parameter relating to a relationship of the virtual channel within the unified discovery interface.
 20. The computer-readable medium of claim 17 wherein the broadcast media content comprises time-based programming content and the non-broadcast media content comprises Internet Protocol content. 